Mobile collection application

ABSTRACT

A mobile collection application is disclosed that is capable of providing collection data to a field agent on a wireless pocket PC. A collection case inventory module is used to generate a list of collection cases on the wireless pocket PC. The field agent may view a detailed report of collection cases that are contained in the list of collection cases. A payment plan component is also provided that allows the field agent to work out a payment plan with the debtor. The mobile collection application is also capable of allowing field agents to register transient taxpayers for the purpose of collecting sales and use taxes.

This application claims the benefit of U.S. Provisional Application Ser.No. 60/402,587, filed Aug. 9, 2002. This application is also acontinuation from and claims benefit of the U.S. Non-Provisionalapplication Ser. No. 10/391,430, filed Mar. 18, 2003 now U.S. Pat. No.7,289,794 which is incorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The present invention relates generally to portable computing and, moreparticularly, to a mobile collection application for wireless terminalsthat allow field agents to retrieve collection case information andinteract with debtors concerning collection accounts.

BACKGROUND OF THE INVENTION

The use of electronic work support tools in the field of collections,and, in particular, in the field of tax collections, has been limitedbecause of the nature and dynamics of field visits. Field collectionvisits are generally brief and typically only last 15 to 20 minutes.They also involve visits with individuals or businesses that may beavoiding payment for various reasons. As such, they may involve hostileinteractions that require collectors to be alert and able to operatequickly. A field agent may need to leave quickly and typically is notprovided with an opportunity to plug-in a laptop computer and sit backand allow time for the computer to boot-up for the collection process.In addition, laptop computers require large amounts of workspace, whichis typically not available to field agents during a field visit.

Field collection visits also require complete information about accountand collection histories that require the collectors to carry printoutsor copies of account and collection histories for various individualsand businesses. Field collection visits may conclude with the acceptanceof payment, establishing a payment agreement, or other legal documentsthat are precursors to stronger collection enforcement actions.

Laptop computers and other similar devices could accommodate the needfor access to information that collectors need in order to addressissues with individuals or companies who are behind in payments.However, the time requirements for “booting up,” the need for largeamounts of desk space, limited battery life and the inability of thecollector to fully interact with the debtor while maintaining completephysical control of the device render laptop computers and similardevices impractical during a collection visit. Since laptop computersare impractical for these types of interactions, many field agents orcollectors still rely on paper printouts to review collection cases withindividuals or businesses.

As such, a need exists for a mobile collection solution that is capableof providing field agents with information about a debtor in a quick andcompact format that allows field agents to resolve delinquency issueswith debtors.

SUMMARY OF THE INVENTION

An embodiment of the present invention discloses a method and system forproviding collection data to a field agent during a field interviewusing a wireless pocket personal computer (PC). During operation, afield agent logs into a mobile collection application located on thewireless pocket PC. In response to the selection of a main menu option,the mobile collection application may retrieve a collection caseinventory from a collection data center server. The collection caseinventory may be retrieved by the use of a wireless access network thatconnects the wireless pocket PC to the collection data center server.The collection case inventory is then displayed on a display of thewireless pocket PC. The field agent can then select a collection caseentry that is listed in the collection case inventory and a detailedcollection case report may be generated on the display of the pocketpersonal computer based on the selected collection case entry.

The detailed collection case report may include a link to a payment plancomponent of the mobile collection application that allows the fieldagent to setup a payment plan with the debtor or taxpayer. The paymentplan component may allow the field agent to enter data items in a formand then will calculate a payment plan as a function of the data itemsthat are entered in the form for that particular payment plan. If thepayment plan is approved by the taxpayer and the field agent, acollection database on the data collection center server may be updatedaccordingly with the details of the payment plan. A printer may beconnected with the wireless pocket PC to printout a receipt for thetaxpayer.

The mobile collection application may also include a collection casesearch component that allows the field agent to search for particularcollection cases within the collection database of the data collectioncenter server. The collection case search component may generate acollection case search form that includes a plurality of searchparameter data entry fields. The field agent will use the searchparameter data entry fields to narrow a search for a particularcollection case. A search results display field may be used to displaysearch results as the field agent begins entering search parameters.

Another embodiment of the present invention discloses a method andsystem for registering taxpayers and collecting taxes in a singleinteraction with a wireless pocket PC being used by a field agent duringa field interview. In this embodiment, a taxpayer registration form isgenerated on a display of the wireless pocket PC. The taxpayerregistration form may include a plurality of taxpayer information dataentry fields that may be filled in by the field agent. A tax calculationform may then be generated on the display of the wireless pocketpersonal computer and the field agent may enter tax information in thetax calculation form using the wireless pocket PC. A total tax amountdue based on the tax information entered in the sales tax calculationform is then calculated by the wireless pocket PC based on apredetermined tax rate. The tax rate may be set by the field agent, thewireless pocket PC or the collection data center server.

The taxpayer information and the total tax amount due may be stored in acollection database on the wireless pocket personal computer or acollection database on the data collection center server.Preferentially, a taxpayer file is created in the collection databaseassociated with the collection data center server based on the taxpayerinformation and the total tax amount due. The tax calculation for may bea sales tax calculation form including a plurality of data entry fieldsthat may be selected from a group of data entry fields including a totalsales data entry field, a taxable sales data entry field, a taxablepurchases data entry field and a tax rate data entry field.

A total amount of tax due display field may be generated on the displayof the wireless pocket PC based on the total tax amount due. A taxverification form may also be generated on the display of the wirelesspocket PC that includes an itemized index field that summarizes thefield interview. A payment processing component of the mobileregistration application may be used by the taxpayer or field agent topay for the total amount of tax due. A receipt may then be printed outwith a printer connected with the wireless pocket PC.

Further objects and advantages of the present invention will be apparentfrom the following description, reference being made to the accompanyingdrawings wherein preferred embodiments of the invention are clearlyillustrated.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system architectural view of a mobile collection system foruse with wireless pocket personal computers.

FIG. 2 illustrates a representative authentication graphical userinterface that is generated by the mobile collection application.

FIG. 3 illustrates a representative main agenda interface graphical userinterface of the mobile collection application.

FIG. 4 is a block diagram illustrating application modules of the mobilecollection application.

FIG. 5 illustrates a representative mobile collection main menugraphical user interface of the mobile collection application.

FIG. 6 illustrates a representative collection case inventory graphicaluser interface generated by the mobile collection module of the mobilecollection application.

FIG. 7 illustrates a representative a collection case search graphicaluser interface of the mobile collection application.

FIG. 8 illustrates a representative collection case display of themobile collection module.

FIG. 9 illustrates a representative collection case detail reportgraphical user interface generated by the collection case inventorycomponent.

FIG. 10 illustrates a payment plan component of the mobile collectionapplication.

FIG. 11 illustrates a representative mobile registration graphical userinterface of a taxpayer registration module of the mobile collectionapplication.

FIG. 12 illustrates a representative tax return information graphicaluser interface of the taxpayer registration module.

FIG. 13 illustrates a representative outlet information graphical userinterface of the taxpayer registration module.

FIG. 14 illustrates a representative sales tax collection graphical userinterface of a sales tax collection module.

FIG. 15 illustrates a representative sales tax calculation graphicaluser interface of the sales tax collection module.

FIG. 16 illustrates a representative supplemental tax graphical userinterface of the sales tax collection module.

FIG. 17 illustrates a representative verification graphical userinterface.

FIG. 18 illustrates a representative tax adjustment graphical userinterface.

FIG. 19 illustrates a representative second tax adjustment graphicaluser interface.

FIG. 20 illustrates a representative adjusted sales tax graphical userinterface.

FIG. 21 illustrates a representative payment processing graphical userinterface of the sales tax collection module.

FIG. 22 illustrates a representative print graphical user interface of aprint module.

FIG. 23 illustrates a representative follow up graphical user interfaceof a follow-up module.

DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EMBODIMENTS OF THEINVENTION

Referring to FIG. 1, a preferred embodiment of the present inventiondiscloses a mobile collection system 100. The preferred mobilecollection system 100 includes a wireless pocket PC 102 that may beconnected to a wireless access network 104. The term wireless pocket PC102 should be broadly construed to include any type of mobile computingdevice that is capable of establishing a wireless connection with a dataserver and allowing a field agent to interact with data files containedon the data server. A non-wireless or standard pocket PC 106 may alsouse the mobile collection system 100 as well by using a docking stationto connect to a personal computer.

In addition to a wireless pocket PCs 102, the present invention may beused in conjunction with personal digital assistants and any mobilecomputing device that may be used as a “dumb terminal”. Someillustrative pocket PCs that may be used by the present inventioninclude the FP iPaq Pocket PC H5450, Audiovox Thera, Toshiba 2032,Siemens/AT&T Wireless SX56, T-Mobile Pocket PC, Compaq iPaq Pocket PCH3760/H3765 and so forth. For the purpose of the present invention, itis important to note that the mobile computing device used is small andcompact, which allows field agents to move quickly in case a field visitturns hostile.

The wireless access network 104 may include a base station 108 that maybe connected to an access network server 110. The access network server110 may include a firewall 112 or the firewall 112 may be installed on acomputer that may be connected with the access network server 110. Arouter 114 may be connected with the access network server 110 and maybe used to send and receive data across a network connection 116. Thenetwork connection 116 may be a virtual private network (VPN), anInternet-based network connection or any other type of networkconnection that may be used to transfer data over a network. Thoseskilled in the art should recognize that several different types ofcomponents and devices may be used to transmit data over a network.

The wireless access network 104 may be connected to a collection datacenter 118. The collection data center 118 may include a collection datacenter server 120 that may be connected with the network connection 116.The collection data center server 120 may include or be connected with acollection database 122. The collection database 122 may include aplurality of data files that relate to individuals or businesses. Forexample, the collection database 122 may include a plurality of taxrecords related to individuals and businesses. However, other types ofcollection records and data may also be contained in the collectiondatabase 122 that relate to a broad range of debtors. The collectiondata center server 120 may also be connected with a router 114 and afirewall 112 to establish the connection between the collection datacenter server 120 and the network connection 116.

Referring to FIG. 2, the mobile collection system 100 includes a mobilecollection application 200 that is installed on the wireless pocket PC102. In one embodiment, whenever the wireless pocket PC 102 is poweredon or rebooted, a field agent may be presented with an authenticationgraphical user interface (GUI) 202. A collection application iconlocated on the desktop of the wireless pocket PC 102 may also start themobile collection application 200. The authentication GUI 202 may promptfield agents to enter a username and a password in a user ID field 204and a password field 206. Upon entering an appropriate username andpassword, the field agent will click on a Login icon 208. A Cancel icon210 may also be included that allows the field agent to exit the mobilecollection application 200.

To authenticate the field agent, the mobile collection application 200may establish a connection to the collection data center server 120.After connecting to the collection data center server 120, thecredentials entered by the field agent may be transmitted to thecollection data center server 120 using the network connection 116. Thecollection data center server 120 includes an authentication applicationthat uses the credentials to authenticate the field agent against amobile user directory that may be contained within the collectiondatabase 122. Although not specifically illustrated, an authenticationserver may be used to authenticate the wireless pocket PC 102. Theauthentication server may be connected to the network connection 116 orthe collection data center server 120.

If the credentials presented by the field agent are valid, then a tokenwith an expiration date may be generated and returned to the wirelesspocket PC 102. If the credentials are invalid, then the field agent willbe informed to attempt to login again. Once the number of login attemptsexceeds a predetermined threshold value, then the account associatedwith that field agent may be locked out and any local collectiondatabase replicas may be automatically deleted from the wireless pocketPC 102. The validated credential set along with the token may beencrypted and cached on the wireless pocket PC 102 until the field agentfinishes the application session or the token automatically expiresafter a predetermined time period. The cached credentials and token arepreferentially used to authenticate the field agent whenever aconnection is established and data is transferred between the wirelesspocket PC 102 and the collection data center server 120.

After the field agent logs into the mobile collection application 200,the collection data center server 120 may download or transfer all orpart of the data related to collection cases that the field agent needsto address or work on directly to the wireless pocket PC 102. Thecollection case information may be stored in the wireless pocket PC 102so that the wireless pocket PC 102 does not have to establish aconnection with the wireless access network 104 in order to retrievedata from the collection data center server 120. In alternativeembodiments, the wireless pocket PC 102 may establish a connection withthe wireless access network 104 each time the field agent needs toretrieve or send data to the collection database 122. Other wirelessaccess networks 104 that may be used by the present invention allowwireless communication devices to constantly be connected to thewireless access network 108 thereby eliminating the need to transfer anydata files to the wireless pocket PC 102 unless requested by the fieldagent during operation.

Referring to FIG. 3, after the field agent has successfully completedthe login process, the mobile collection application 200 may launch amain agenda interface module 300. The main agenda interface module 300may generate an agenda interface GUI 301 on the display of the wirelesspocket PC 102. The agenda interface GUI 301 may be the desktop or maininterface from which field agents interact with the mobile collectionapplication 200. The agenda interface GUI 301 may include a brandedtheme and links to all of the core applications or tools that are usedby the field agent during the course of a normal workday. The brandedtheme may be represented as an icon, an animated icon, a trademark, aservice mark or any other type of name, symbol, or device that may beused to designate a source. FIG. 3 represents an illustrativeimplementation of the mobile collection application 200 for the Officeof ABC Agency for the State of Texas, which should not be construed as alimitation of the present invention.

The agenda interface GUI 301 may be broken into a plurality of key worksections or groupings where a single tap or selection of the screen orthe selection of a work section with a pointing device will launch oractivate each software module or tool represented by the selected worksection or grouping. The work sections or groupings may be in the formof icons or text or a combination of both. The applications or toolsprovided in the work sections could be setup or designed in severaldifferent formats.

Referring collectively to FIGS. 3 and 4, the agenda interface GUI 301may include several work sections that provide links to software modulesthat may include a mobile enablement module 302, a mobile collectionmodule 304, a terminal emulator module 306, an intranet module 308, anemail module 310, a personal task list management module 312 and apersonal calendar module 314. The agenda interface GUI 301 acts as amain menu to the modules or tools that are provided within the mobilecollection application 200. Solutions for different companies, agenciesand types of field agents may require modification of the number ofsoftware modules that are presented to the field agents through thewireless pocket PC 102. As such, other software modules may also beincluded in the agenda interface GUI 301.

The mobile enablement module 302 provides a help desk application thatprovides links to information about application support, links totechnical information, links to a consumable reordering application(e.g.—for ordering paper, ink and styluses) and links to answers offrequently asked questions about the mobile collection application 200.The help desk application may be presented in a searchable HTML formaton the wireless pocket PC 102. A browser may be used to present theinformation contained in the mobile enablement module 302 to the fieldagent.

The wireless pocket PC 102 may receive most of the information andservices provided by the help desk application from the collection datacenter server 120. The data may be stored on the collection data centerserver 120 or on another server connected with the network connection116 and transmitted to the wireless pocket PC 102 in several differenttypes of file formats, such as an active server page for instance.Varying amounts of information provided by the help desk application maybe stored on the wireless pocket PC 102. The information stored on thewireless pocket PC 102 may be updated by the collection data centerserver 120 as necessary or on a regularly scheduled basis.

The terminal emulator module 306 provides a terminal emulator thatallows the wireless pocket PC 102 to emulate a particular type ofterminal in order to gain access to data that may be stored on thecollection data center server 120. The terminal emulator module 306 mayallow the wireless pocket PC 102 to establish a connection with a legacydata system or application (not illustrated) that may be located on thecollection data center server 120 or connected with the collection datacenter server 120. This allows the field agent to access data containedon legacy systems or applications that may be required to obtain orupdate needed information or data. The wireless pocket PC 102 mayconnect to the collection data center server 120 to obtain or updateinformation or data through the terminal emulator as needed or to run anapplication on the collection data center server 120.

The intranet module 308 provides a link or bookmark to key intranetinformation or data files that may be used by the field agents. Theinformation provided through the intranet module 308 may be company oragency news items, a periodic bulletin or a news flyer or other types oforganizational information. The information provided by the intranetmodule 308 may be provided in a web page format, a text-based format orin any other suitable type of data format. In one embodiment, theinformation may be provided to the field agents using a browser that isinstalled on the wireless pocket PC 102.

The email module 310 provides access to an electronic mail applicationthat is associated with the field agent using the mobile collectionapplication 200. The email module 310 allows the field agent to accesselectronic mail and provides the field agent with the ability to sendand receive electronic mail using the wireless pocket PC 102. Duringoperation, the email module 310 synchronizes the email account inbox onthe wireless pocket PC 102 with an email account that may be located onthe collection data center server 120. Neither the email account nor theemail application have to be stored on the collection data center server120 and may be stored or provided by another server or third-party thatis connected with the collection data center server 120 or the networkconnection 116.

The personal task list module 312 is responsible for generating a listof personal tasks that are managed and maintained by the field agent.The personal tasks may be entered by the field agent using a taskmanagement interface provided by the personal task list module 312.Personal tasks for a particular field agent may also be entered by aperson located in the home or regional office of the field agent. Forexample, a personal assistant of the field agent may enter a task forthe field agent if the field agent is out of the office.

Although not illustrated, a task list management application located onthe collection data center server 120 may be used by third-parties toenter personal tasks for a particular field agent. This allows a fieldagent to receive an assigned task list that may be stored and displayedon the wireless pocket PC 102. The personal tasks associated with arespective field agent may be stored on the wireless pocket PC 102, thecollection data center server 120 or any other type of data storagedevice connected with the network connection 116. The personal task listassociated with a field agent may be updated at login, periodicallythroughout a session or whenever a third-party enters a task using thetask list management application.

The personal calendar module 314 provides an electronic calendar to thefield agent. The personal calendar module 314 may also allow the fieldagent to enter, modify and delete notes on particular dates contained inthe calendar. The calendar may contain a list of personal calendarevents and reminders that are managed and maintained by the field agent.The items contained in the calendar may be stored on the wireless pocketPC 102, the collection data center server 120 or any other type of datastorage device connected with the network connection 116. In addition,the events listed in the calendar may also be modified by a field agentcalendar interface located on the collections data center server 120.This also allows other individuals to enter items on a field agent'scalendar. The collection data center server 120 may update a fieldagent's wireless pocket PC 102 at login or periodically throughout asession.

Referring to FIG. 5, selection of the mobile collection module 304 ofthe mobile collection application 200 may generate a collection mainmenu GUI 500. The collection main menu GUI 500 includes a plurality ofselection icons that are capable of providing field agents with accessto other tools or components of the mobile collection application 200.These components may include a collection case inventory component 502,a payment plan calculator component 504, a department policies component506, a synchronization utility component 508 and an exit component 510.Selection of any of these selection icons starts the correspondingcomponent of the mobile collection application 200. The exit component510 may return the mobile collection application 200 to the agendainterface GUI 301 or exit the mobile collection application 200entirely.

Referring to FIG. 6, if a field agent selects the selection icon that isassociated with the collection case inventory component 502, the mobilecollection application 200 may start a collection case inventorycomponent 600. The collection case inventory component 600 may generateand display a collection case inventory GUI 602 on the wireless pocketPC 102. The collection case inventory GUI 602 may include a list ofcollection cases 604. The list of collection cases 604 may be collectioncases that are assigned to the field agent or collection cases that arepresented in numeric or alphabetical order. The list of collection cases604 may also be a quick summary of the field agent's workload for aparticular day, week or designated period of time. The list ofcollection cases 604 may be generated as a function of the field agent'spersonal task list or a personal calendar. Several different collectioncases may be included in the list of collection cases 604 and severaldifferent screens may be required to view the entire list or a scrollbar may be used to scroll through the list of collection cases 604.

To generate the list of collection cases 604, the wireless pocket PC 102may connect to the collection data center server 120 and retrieve therequired information from the collection database 122 on an as-neededbasis. The list of collection cases 604 may be transferred to thewireless pocket PC 102 when the field agent selects the collection caseinventory component 502. In the alternative, the wireless pocket PC 102may connect to the collection data center server 120 at a predeterminedperiod of time and download or replicate the collection data requiredfor use by a particular field agent on the wireless pocket PC 102. Asset forth in greater detail below, the field agent may also use acollection case search query field 606 to retrieve data about aparticular collection case.

Although not illustrated, a collections application on the collectiondata center server 120 may be operable to generate the list ofcollection cases 604 that are assigned to the field agent for any givenperiod of time or as requested by the field agent. The collectionsapplication may assign delinquent accounts to field agents for thepurpose of the field agent attempting to collect money owed or to workout a payment plan during a field visit with individuals or businesseshaving delinquent accounts. The collections application is responsiblefor responding to requests for information that are generated by thewireless pocket PC 102 by locating the information from the collectiondatabase 122 and sending the corresponding data back to the wirelesspocket PC 102.

As illustrated in FIG. 6, the list of collection cases 604 may beorganized and displayed to the field agent using a case identification(ID) 608 and a case name 610. The collection case inventory component600 may also include a collection case search query field 606 thatallows the field agent to look up or retrieve collection casesinformation for individuals or businesses that are not listed in thelist of collection cases 604 that may be generated by the collectioncase inventory application 600. The field agent may enter a case ID 608or a case name 610 (business name) in the entry field provided by thecollection case search query field 606 in order to retrieve a particularcollection case.

Referring to FIG. 7, selection of the collection case inventorycomponent 502 may start a collection case search component 700. Thecollection case search component 700 may generate a collection casesearch GUI 702. The collection case search GUI 702 may include aplurality of collection case data entry fields 704 that allow the fieldagent to locate and retrieve collection case data that may be stored inthe collection database 122. The collection case data entry fields 704may include a name entry field 706, a taxpayer identification (ID) entryfield 708, a phone number entry field 710, a city entry field 712 and azip code entry field 714.

The field agent may enter data in one or more of the fields contained inthe collection case data entry fields 704 to search for a particularcollection case or entity. A search results field 716 may also beincluded in the collection case search GUI 702 that displays the resultsto a search request that may be entered by the field agent. Although notspecifically illustrated, the search results may also be displayed in aseparate window or GUI if the search results field 716 is not present inthe collection case search GUI 702.

A search request may be entered by selecting one of the data entryfields 704 and entering data that may be relevant for that particulardata entry field 704. In FIG. 7, the city of Dallas has been enteredinto the city entry field 712 for illustrative purposes only. Once datahas been entered in at least one of the data entry fields 704, the fieldagent may select a Search icon 718 on the collection case search GUI 702that causes the collection case search component 700 to transmit asearch request to the collection data center server 120.

In response to the search request sent by the wireless pocket PC 102, asearch result may be generated by the collection data center server 120that is responsive to the search request entered by the field agent. Thesearch result may be obtained by the collection data center server 120by locating the requested information in the collection database 122.Once the requested data is located, the search result may be transmittedto the wireless pocket PC 102 from the collection data center server120.

The wireless pocket PC 102 may then display the search results in thesearch results field 716 or on a separate search results GUI. Referringcollectively to FIGS. 6 and 7, the field agent may select a collectioncase from the list of collection cases 604 or from the search resultslisted in the search results field 716. As set forth in greater detailbelow, after selecting a respective collection case, details about theselected collection case are displayed to the field agent on thewireless pocket PC 102.

As illustrated in FIG. 7, a Reset icon 720 may clear data entries thathave been placed in the data entry fields 704. This allows the fieldagent to enter another search using the data entry fields 704 if thefirst search did not retrieve the desired collection case. The Reseticon 720 may also clear search results that are generated and displayedin the search results field 716. As such, during operation the Reseticon 720 may be used to start or initiate a new search for a collectioncase of interest by the field agent.

Referring to FIG. 8, selection of a collection case from the list ofcollection cases 604 or the search results field 716 may start orinitiate a case display component 800. The case display component 800may generate a case display GUI 802. The case display GUI 802 mayinclude a case information field 804 and a case detail selection field806. The case information field 804 may include a name field 808, anidentification (ID) field 810, an address field 812, a city field 814, astate field 816, a zip code field 818 and a phone number field 820. Theinformation provided in all of these fields may be sent from thecollection data center server 120 or already stored on the wirelesspocket PC 102 if the collection data was already transferred from thecollection data center server 120.

The case detail selection field 806 may include a Main selection icon822, a Detail selection icon 824, a Contact selection icon 826, a Casesselection icon 828, an Account selection icon 830 and an UnscheduledInteractions selection icon 832. The Main selection icon 822 isassociated with the case display GUI 802 set forth in FIG. 8. Asillustrated, general information about the entity associated with thecollection case is displayed in the case display GUI 802.

Although not illustrated in FIG. 8, selection of the Detail selectionicon 824 may generate a collection case detail GUI (see FIG. 9) thatprovides various types of additional data about the entity beinganalyzed by the field agent. The collection case detail GUI provides adetailed collection case report. The Contact selection icon 826 maygenerate a contact GUI that may provide information about managerialpersonnel at the entity. The Cases selection icon 828 may generate acase GUI that provides details about current cases associated with theentity. The Account selection icon 830 may generate an account GUI thatprovides information about the type of collection accounts that areassociated with the entity and a history of the account. The UnscheduledInteractions selection icon 832 may generate an interaction GUI thatprovides details of unscheduled visits to the entity and also mayprovide an input section that allows the field agent to inputinformation about his or her visit or schedule further unscheduledvisits with the entity in question.

Referring to FIG. 9, if the field agent selects the case detailselection icon 824, a collection case detail component 900 may generatea collection case detail GUI 902 on the wireless pocket PC 102. Thecollection case detail component 900 may generate a detailed collectioncase report about the selected collection case. The collection casedetail GUI 902 may also be generated at any point in time in which acollection case is selected. As illustrated, the collection case detailGUI 902 may summarize the collection case demographics, outstandingbills, and payment information for the selected collection case orentity.

Referring to FIGS. 1 and 9, to generate the collection case detail GUI902, the wireless pocket PC 102 may connect to the collection datacenter server 120, which retrieves the information or account data fromthe collection database 122. In the alternative, the information oraccount data for each collection case assigned to a respective fieldagent may have previously been transferred to the wireless pocket PC102, which may occur at login or any other predetermined synchronizationperiod.

As illustrated in FIG. 9, the preferred collection case detail GUI 902may display the case ID 904 and the case name 906. In addition, thecollection case detail GUI 902 may include an address listing 908, atelephone listing 910, a case type listing 912, a case status listing914, a case balance listing 916 and an outstanding bills field 918. Theoutstanding bills field 918 may include a listing of all of theoutstanding bills and liabilities for the entity in question. Asillustrated, the outstanding bills field 918 set forth in FIG. 9includes a liability number, a tax type indication, a period indicationand a liability amount indication for each respective type of liabilityor debt owed. Other information or data may also be listed in theoutstanding bills field 918 and as such, the outstanding bills field 918set forth in FIG. 9 should not be viewed in an illustrative sense andshould not be construed as a limitation of the present invention.

Although not specifically illustrated, a payment history listing mayalso be displayed in the collection case detail GUI 902, as well as anyother relevant information. In addition, although not specificallyillustrated the field agents may also have the ability to drill-down onindividual liabilities in a case and retrieve more specific detailsabout a particular liability listing. The collection case detail GUI 902may also include a payment plan selection icon 920 that leads fieldagents to a payment plan component 1000, which is set forth in FIG. 10.As set forth above, the wireless pocket PC 102 may connect to thecollection data center server 120 and retrieve information from thecollection database 122 using one of the several means of data transferacross the wireless access network 104 set forth above.

Referring to FIG. 10, the payment plan component 1000 may generate apayment plan GUI 1002 that allows field agents to calculate and createpayment plans with debtors. As illustrated, selection of the paymentplan selection icon 920 in the collection case detail GUI 902 brings upthe payment plan GUI 1002 of the mobile collection application 200. Thepayment plan component 1000 allows field agents to calculate proposedpayment plans based upon payment plan frequency and amount due in orderto work out an acceptable payment plan with the debtor. The payment planpresented to the entity may be calculated according to preset guidelinesstored in the collection data center server 120 or the wireless pocketPC 102. As illustrated, the payment plan GUI 1002 may include a caseidentification (ID) field 1004, a case name field 1006 and a casebalance field 1008.

In order to setup a payment plan, the field agent may enter a downpayment in a down payment field 1010, an installment payment in aninstallment payment field 1012 and/or a payment frequency in a paymentfrequency field 1014. The down payment field 1010 may allow the fieldagent to enter an amount that will be paid by the debtor at thatparticular time or as a down payment on the debt that is owed. Theinstallment payment field 1012 may allow the field agent to enter anamount that the debtor feels they can pay in installments to satisfy theoutstanding debt. The payment frequency field 1014 may allow the fieldagent to choose a time period in which payments should be made such asweekly, monthly quarterly or yearly for example.

Based on the values of the above-referenced entries, the payment plancomponent 1000 is operable to calculate a payment plan once a Calculatepayment plan icon 1016 is selected by the field agent. The payment plancomponent 1000 may also calculate the payment plan as the entries areentered thereby eliminating the need for the Calculate payment plan icon1016. Once the calculate payment plan icon 1016 is selected, a paymentplan details field 1018 may display the details of the payment plan tothe field agent for discussion and review with the debtor.

The payment plan component 1000 may then display a first payment amount1020, an installment payment amount 1022 and a payment term 1024. If thepayment plan is acceptable to the debtor, the field agent may select aSubmit payment plan icon 1026 on the payment plan GUI 1002 that maycause the wireless pocket PC 102 to transmit the details of the paymentplan to the collection data center server 120 for approval.

If the payment plan is accepted or approved, the collection data centerserver 120 will transmit an acknowledgment to the wireless pocket PC 102and update the collection database 122 with the details of the paymentplan as it relates to that particular debtor. The wireless pocket PC 102can also wait to submit the payment plan to the collection data centerserver 120 at a later point in time as well. Although not specificallyillustrated, if the payment plan is approved the wireless pocket PC 102may generate a payment plan receipt that is printed on a printerconnected with the wireless pocket PC 102 that may be kept for thedebtors records.

Referring once again to FIG. 5, the collection main menu GUI 500 of themobile collection application 200 may also include a selection icon thatprovides a link to the payment plan GUI 1002. As set forth in detailabove, the payment plan component 1000 allows the field agents topresent various types of payment plans to the debtor in an attempt toworkout an acceptable payment arrangement with the debtor. If anacceptable payment plan is worked out, it is submitted to thecollections data center server 120 for approval. The collection datacenter server 120 may includes a payment plan approval application thatverifies that the proposed payment plan does not violate any departmentpolicies and so forth. If the payment plan is approved, the collectiondatabase 122 is updated to reflect that the debtor has approved thepayment plan.

The collection main menu GUI 500 may also includes a selection icon thatprovides a link to a department policies component 506. Although notspecifically illustrated, the department policies component 506 mayprovide a plurality of links to information and data files that arestored on web pages on the collection data center server 120 or thewireless pocket PC 102. This information can be used by field agents tolocate answers to questions that relate to the policies of theparticular enterprise that is using the mobile collection system 100.

As further illustrated in FIG. 5, the collections main menu GUI 500 mayalso include a synchronization utility component 508. Thesynchronization utility component 508 may be used to synchronize thewireless pocket PC 102 with the collections data center server 120.Since the wireless pocket PC 102 does not necessarily have to beconnected with the wireless access network 104 at all times, the fieldagent may modify data files that have been transferred to the wirelesspocket PC 102 from the collections data center server 120 when dealingwith debtors throughout the course of a day. At the end of the day orany other relevant time, the collection files that have been entered ormodified may need to be transferred back to the collections data centerserver 120 so that the modifications or new entries can be stored in thecollection database 122.

Referring once again to FIG. 1, the wireless pocket PC 102 maysynchronize regularly with the collection database 122 located on thecollection data center server 120. As set forth above, field agents willbe able to selectively download collection cases to which they areassigned from the collection data center server 120 as well as variousother types of information. After working cases by conducting fieldvisits with the debtors, information that field agents have recorded canthen be uploaded and posted back to the collection database 122.Preferentially, there may be two options for exchanging or synchronizingdata from the wireless pocket PC 102 to the collection data centerserver 120.

First, with a desktop synchronization option, data is transferredbetween the wireless pocket PC 102 and the collection database 122 onthe collections data center server 120 by physically connecting thewireless pocket PC 102 to the network connection 116. As illustrated inFIG. 1, with this synchronization option, the wireless pocket PC 102 isconnected to a desktop terminal 124 that is connected to the networkconnection 116. For example, the wireless pocket PC 102 may connect tothe desktop terminal 124 through a USB connection or a docking station.This may be the most secure method of synchronizing collection databetween the wireless pocket PC 102 and the collection data center server120.

Another way of synchronizing the collection data is through the use of asecure wireless connection. This process would be similar to desktopsynchronization, but could occur outside of central offices as a fieldagent is connected over a secure line, such as a wireless virtualprivate network (VPN). Similar to dial-up VPN connections, the wirelesspocket PC 102 connect through secure “tunnels” and exchange encryptedmessages that only the collection data center server 120 and thewireless pocket PC 102 can “unlock”.

In the preferred embodiment of the present invention, the mobilecollection system 100 seamlessly integrates core collection data andmakes this information available to field agents. The use of thewireless pocket PC 102 eliminates the need for issuing costly and largelaptop computers to field agents. The mobile collection system 100 iseasy to use and reduces the training time of new field agents. Inaddition, the mobile collection system 100 reduces the dependence onpaper-based collection cases as all critical information aboutcollection accounts can be accessed by the wireless pocket PC 102. Themobile collection system 100 provides field agents with effectiveorganizational and time management tools that are included on thewireless pocket PC 12. Wireless connectivity enables field agents tohave access to current, up-to-date account information at any time.

A wireless pocket PC 102 not only more effectively meets the needs offield agents than a laptop computer; it also greatly improves theefficiency and effectiveness of the field agent. It enables the fieldagent to conduct and complete all aspects of the collection visit andthe resolution of the delinquent account without the need to return tothe office or revisit the debtor.

In addition to the routine collection activities described, the mobilecollection application 200 will support other compliance activitiesconducted in the field, such as validating licenses and registrations,registering and licensing taxpayers, and the preparation and filing oftax returns remotely. Field agents are able to remotely look-up theregistration and account status of individuals and business notspecifically included in their collection case inventory. For instance,at state fairs and other events, field agents can verify the validity ofregistration information, identify tax periods for which returns havenot been filed, and identify outstanding liabilities. The mobilecollection application 200 may include functions that enable fieldagents to remotely register a new business and electronically prepareand accept tax returns at the location of the taxpayer, whether that isan established business location or a temporary/location such as a boothat a fair or similar event.

Referring to FIG. 11, the mobile collection application 200 may alsoinclude a taxpayer registration module 1100 that allows a field agent toregister taxpayers at remote locations. The taxpayer registration module1100 allows for the registration of permits, licenses and tax paymentinformation from a remote location (i.e.—registration of a transitoryvendor at locations such as state fairs, art shows, festivals, fleamarkets or any other type of non-office based vendor). The taxpayerregistration module 1100 enables completing the registration processprior to the end of the event, which would not be practical without aremote real time mobile application.

In other embodiment of the present invention, the taxpayer registrationmodule 1100 may be used to register individuals for permits and licensesto operate at specific locations. As such, in this embodiment, if avendor needs a permit or license to operate at a specific event, thefield agent may use the wireless pocket PC 102 to register the vendor.In addition, the field agent may use the wireless pocket PC 102 to printa permit or license for the specific vendor to operate during the event.A printer connected to the wireless pocket PC 102 may be used to printthe permit and the information entered by the field agent will betransmitted to the server 120 for storage in the database 122. The fieldagent is capable of creating a record for transient or one-time vendorsthat participate in events.

The taxpayer registration module 1100 may generate a mobile registrationGUI 1102 on the wireless pocket PC 102 using a taxpayer registrationcomponent. The mobile registration GUI 1102 may include a business nameentry field 1104, a taxpayer identification (ID) field 1106, an addressentry field 1108, a city field 1110, a state entry field 1112, a zipcode entry field 1114 and a country entry field 1116. The field agentmay use the mobile registration GUI 1102 to input information about ataxpayer in the provided fields, which allows the collection data centerserver 120 to create a record in the collection database 122 associatedwith that particular taxpayer or entity. The value placed in thetaxpayer ID field 1106 may automatically be generated by the collectiondata center server 120. The wireless pocket PC 102 may transmit the datathat is entered to the collections data center server 120 as it isentered or at any periodic time. To proceed to the next section of theregistration process, the field agent may select a Next icon 1118 or maysave the record or go back to another section by selecting a Back icon1120.

Referring to FIG. 12, the taxpayer registration module 1100 may includea return information component 1200. The return information component1200 may generate a return information GUI 1202. The return informationGUI 1202 may include a filing period section 1204 and a due date section1206. These sections may be automatically set to predetermined dates orset by the field agent during a field interview with the taxpayer. Inaddition, if the entity is no longer in business, the field agent mayselect a termination icon 1208 and enter a date of termination in a dateof termination entry field 1210. A specific location icon 1212 may alsobe included to provide a link to an additional GUI that allows theentity to indicate the number of locations that may be out of business.To proceed to the next section of the registration process, the fieldagent may select a Next icon 1214 or may save the record or go back toanother section by selecting a Back icon 1216.

Referring to FIG. 13, the taxpayer registration module 1100 may alsoinclude an outlet information component 1300 that allows the taxpayerentity to verify the location that they are registering or making apayment for as some entities may have several outlets or locations. Theoutlet information component 1300 may generate an outlet information GUI1302. The outlet information GUI 1302 may allow the field agent to enteror modify information about a particular outlet. The field agent mayenter outlets and their respective addresses in an outlet number field1304 and an address field 1304 or review all of the taxpayer's existingoutlet information. In other embodiments, the field agent may enter anoutlet number and the information may appear in the outlet address field1306. To proceed to the next section of the registration process, thefield agent may select a Next icon 1308 or may save the record or goback to another section by selecting a Back icon 1310.

Referring to FIG. 14, the mobile collection application 200 may alsoinclude a sales tax collection module 1400. The sales tax collectionmodule 1400 may generate a sales tax information GUI 1401 on thewireless pocket PC 102. During a field visit, the field agent may entera total sales amount in a total sales amount field 1402. The total salesentered may be for one particular outlet or more than one outlet orlocation. A taxable sales amount may also be entered in a taxable amountfield 1404. In addition, a taxable purchase amount may also be enteredin a taxable purchases field 1406. Again, to proceed to the next sectionof the registration process, the field agent may select a Next icon 1408or may save the record or go back to another section by selecting a Backicon 1410.

Referring to FIG. 15, the sales tax collection module 1400 may alsoinclude a state tax calculation component 1500. The state taxcalculation component 1500 may include a state tax information GUI 1502that includes an amount subject to tax field 1504. The amount subject totax field may be calculated based on the items entered in the sales taxcollection module 1400. A state tax rate field 1506 may be included thatindicates the tax rate associated with the particular transaction orproduct the field agent is processing during the field visit. The taxrate in the state tax rate field 1506 may be automatically generated,selected from a list of tax rates or entered by the field agent.

An amount of tax due may be listed in an amount of tax due field 1508 ofthe state tax information GUI 1502. If the field agent has to select thetax rate, the field agent may use a Calculate icon 1510 to have thestate tax calculation module 1500 calculate the amount of tax due or itmay occur automatically after the tax rate is selected. As such, themobile collection application 200 includes a tax calculation applicationthat allows field agents to determine taxes that are due on the spot,which is especially helpful for transient vendors that do not havepermanent business locations. A Next icon 1512 may be included forproceeding to the next section and a Back icon 1514 may be included forreturning to the previous section.

Referring to FIG. 16, the sales tax collection module 1400 may include asupplemental tax calculation component 1600 that may be an extension ofthe state tax calculation component 1500. The supplemental taxcalculation component 1600 may generate a supplemental tax GUI 1602 onthe wireless pocket PC 102. The supplemental tax GUI 1602 may include acity/transit/county/SPD name entry field 1604, a city/transit/county/SPDnumber entry field 1606, an amount subject to tax field 1608, a tax ratefield 1610, and an amount of tax due field 1612. The field agent mayenter any of the items listed in the supplemental tax GUI 1602 or thecollections data center server 120 may automatically enter them. Thesupplemental tax calculation component 1600 may also include an addsupplemental tax icon 1614 that allows the field agent to add additionalsupplemental tax data. An OK icon 1616 may be used by the field agent toproceed to the next section or a Back icon 1618 may be used to go backto a previous section.

Referring to FIG. 17, the sales tax collection module 1400 may alsoinclude a verification component 1700 that may generate a taxverification GUI 1702 on the wireless pocket PC 102. The taxverification GUI 1702 may include an itemized tax field 1704, a Modifyicon 1706, a View icon 1708, a Delete icon 1710, an OK icon 1712 and aBack icon 1714. The itemized tax field 1704 may include a list of all ofthe tax liabilities that are due for that particular outlet or entity.Other information may be included in the itemized tax field 1704 aswell, such as an identification number, an outlet number and a total taxdue indication. The verification module 1700 may verify taxes for oneoutlet, several outlets or an entire business entity.

The Modify icon 1706 allows the field agent to go back and modifyinformation that may have been entered in previous sections if an erroror problem has occurred. The View icon 1708 may allow the field agent toview a list of the supplemental tax items that are associated withtaxpayer. The Delete icon 1710 may allow the field agent to delete therecord that has been created for the taxpayer. The proceed or OK icon1712 allows the field agent to complete the session with the taxpayer.The Back icon 1714 allows the field agent to go back to a previoussection or GUI.

Referring to FIG. 18, the sales tax collection module 1400 may alsoinclude a tax adjustment component 1800 that may allow the field agentto enter any adjustments to the amount of taxes owed by the taxpayer. Atax adjustment GUI 1802 may be generated by the tax adjustment component1800 that may include a total tax due field 1804, a prepayment field1806, a payment credit field 1808 and an adjusted tax due field 1810.The tax adjustment component 1800 allows the field agent to adjust thetotal tax due by deducting prepayment amounts and credit amounts. Theadjusted tax due is then calculated by the tax adjustment component 1800and displayed in the adjusted tax due field 1810 once a Calculate icon1812 is selected by the field agent. Again, the tax adjustment component1800 may calculate the adjusted tax due automatically without thenecessity of selecting the Calculate icon 1812. A Next icon 1814 may beincluded for proceeding to the next section and a Back icon 1816 may beincluded for returning to the previous section.

Referring to FIG. 19, the tax adjustment component 1800 may also includeadditional items that are displayed on a second tax adjustment GUI 1902.The second tax adjustment GUI 1902 may include a timely filing discountfield 1904, a prior payment field 1906, a net tax due field 1908, apenalty field 1910, and a total tax amount due field 1912. Sometaxpayers or governing bodies may offer discounts for timely payment oftaxes or offer the taxpayer the ability to make prior payments. Somelocations may offer other types of discounts or no discounts at all.Various other types of tax adjustments may be available for a variety ofreasons and are envisioned by the present invention.

After these amounts are deducted, the tax adjustment component 1800 maygenerate a net tax due, which is illustrated in a net tax due field1908. If there is a penalty associated with the taxpayer's account thisamount may be indicated in a penalty field 1910 and then added to thenet tax due. The total tax amount that is due may then be set forth in atotal tax amount due field 1912. A Calculate icon 1914 may be used bythe field agent to calculate the total tax amount due or the taxadjustment application 1800 may do it automatically as values areentered. To proceed to the next section, a Next icon 1916 may beselected by the field agent or the field agent may go back to a previoussection by selecting a Back icon 1918.

Referring to FIG. 20, an adjusted sales tax component 2000 of the salestax collection module 1400 may generate an adjusted tax GUI 2002 thatsets forth the adjusted total tax. The adjusted tax GUI 2002 may includea total amount paid field 2004 that illustrates the total amount of taxthat will be paid by the taxpayer. A date field 2006 may be includedthat allows the field agent to enter the date that the taxes are beingpaid, which may be set automatically to the current date. A phone numberfield 2008 may also be included that allows the field agent to enter atelephone number of the location the field agent is visiting. To proceedto the next section, a Next icon 2010 may be selected by the field agentor the field agent may return to a previous section by selecting a Backicon 2012.

Referring to FIG. 21, the sales tax collection module 1400 may include apayment processing component 2100 that may generate a payment processingGUI 2102 on the wireless pocket PC 102. The payment processing GUI 2102may include a case summary field 2104, a payment field 2106, a signaturefield 2108, a Submit icon 2110, a Back icon 2112 and a Clear Signatureicon 2114. The case summary field 2104 may include a case numberindication field 2116, a balance indication field 2118 and a businessname field 2120. These items generally summarize what the taxpayer isbeing charged taxes for and the amount of taxes being charged to theentity set forth in the business name field.

The payment field 2106 allows the field agent to indicate the manner inwhich the taxpayer is paying for the taxes being assessed. The paymentfield 2106 may include a payment type selection icon 2122 that allowsthe field agent to indicate the manner in which the taxpayer is payingfor the taxes being assessed. Although a check payment is indicated inFIG. 21, other payment types may also be allowed such as cash or creditcard. A check number field 2124 may be included that allows the fieldagent to enter a check number. If payment is being made with a creditcard, this field may be a credit card number field and an expirationdate field may also be included. A payment amount field 2126 may also beincluded that indicates the total amount being paid by the taxpayer. Theamount being paid may actually different from the total balance owed ifthe taxpayer cannot satisfy the entire amount at that particular time.

The signature field 2108 allows the taxpayer to provide a digitalsignature that is captured by the payment processing module 2100 andtransmitted to the collections data center server 120 for storage in thecollections database 122. This verifies that the taxpayer reviewed theamount of tax owed and agreed to payment using one of the paymentoptions that may have been selected. The Submit icon 2110 allows thefield agent to submit the details of the interaction to the collectiondata center server 120. The collection data center server 120 thenupdates the appropriate records or adds the record of the transactionwith the taxpayer in the collection database 122. The Back icon 2112allows the field agent to go back to the previous section and the ClearSignature icon 2114 allows the field agent to clear the signature out ofthe signature field 2108.

Although not specifically illustrated, the payment processing component2100 may also be modified to operate as a validation component. Thevalidation component may be used by the field agent to allow a vendor orbusiness person to sign for payment agreements, to validate registrationchanges, to validate new registrations, and, of course, for filing.

Referring to FIG. 22, a print module 2200 of the mobile collectionapplication 200 allows the field agent to print a paper copy of thescreen or report that may be provided to the business entity for theirrecords. Although not illustrated, the wireless pocket PC 102 may beconnected with a printer. The wireless pocket PC 102 may use a wirelessconnection with the printer using a communication protocol such asBluetooth. The print module 2200 may include a printer field 2202, aport field 2204, a color selection field 2206, a paper size field 2208,an orientation field 2210, and a custom paper type field 2212. Thoseskilled in the art would recognize the functionality of each of thefields set forth above in the printer application 2200. Selecting aStart Printing icon 2214 will cause the wireless pocket PC 102 totransmit the appropriate data to the printer to make the desiredprintout. A More Settings icon 2216 will provide a link to more printingoptions and the Cancel Printing icon 2218 will cancel the print job.Various receipts and records may be printed by the print application2200.

Referring to FIG. 23, the mobile collection application 200 may alsoinclude a follow up visit scheduling module 2300. The follow-up visitscheduling module 2300 may generate a follow up GUI 2302 on the wirelesspocket PC 102 that allows the field agent to enter various types ofinformation. The follow up GUI 2302 may include a follow up typeselection field 2304, a date field 2306, a period field 2308, a phonenumber field 2310 and a notes field 2312. A Save icon 2314 is providedthat may save the follow up information in the wireless pocket PC 102and/or the collection database 122. The mobile collection application200 may also automatically update the field agent's task list andcalendar to reflect the scheduled follow up visit as well.

Although not specifically illustrated, the mobile collection application200 may also include a voice-over IP (VoIP) application. The VoIPapplication may route telephone calls to and from field agents in thefield. It allows for real time communication between the field agent andany other telephonic device (i.e. having an addressable IP address (i.e.another VoIP device) or phone number). It also enables central officestaff to route incoming calls to field agents via the wireless pocket PC102 without requiring the use of a separate cellular telephone. This isless expensive and more convenient than a mobile telephone.

Although not illustrated, the mobile collection application 200 may alsoinclude an investigation application. The investigation applicationprovides mobile support for field investigations—involving criminalactivities and bootlegging associated with tobacco products, motorfuels, and beer, wine, and spirits. The wireless pocket PC 102 allowsfor real time data base lookup of individuals, tax stamps, or otherpertinent information that is stored in the host database that will beused in the enforcement of applicable laws. Access to taxpayer andreturn data will enable field investigators to work more efficiently andquickly determine when continued surveillance is necessary orunwarranted. In addition, it provides a means to validate informationdiscovered during an investigation and to modify enforcement actions asappropriate.

Although not specifically illustrated, it is worth noting that an inputdevice may be used by the field agent to enter data values in thevarious fields that are used by the mobile collection application 200.The input device may comprise a stylus or pointing device that is usedin conjunction with a touch-screen display of the wireless pocket PC 102or a miniature keyboard that is design to be connected with the wirelesspocket PC 102.

In addition, it is also worth noting that several of the modules andcomponents provided by the mobile collection application 200 may belocated on the collection data center server 120. During operation, thecollection data center server 120 may transmit the functionality of themodules and components to the wireless pocket PC 102 using the wirelessaccess network 104. For example, the mobile collection application maybe run as an active server page in a browser on the wireless pocket PC102. As such, the wireless pocket PC 102 may operate as a dumb terminaland merely process information that is transmitted to it from thecollection data center server 120. The wireless pocket PC or terminal102 may provide a web interface to the mobile collection application200.

Although not specifically illustrated, each of the software modules andcomponents referred to above is designed to generate GUIs that optimallyfit within a display of the wireless pocket PC 102. In a server-basedsolution, the software modules and component are designed to generateGUIs on the display of the wireless pocket PC 102 in a manner that fitsthe technical specifications of the display of the wireless pocket PC102. As such, the GUIs that are generated on the display of the wirelesspocket PC 102 are tailored to fit within the display of the device thatis being used by the field agent.

While the invention has been described in its currently best-known modesof operation and embodiments, other modes, embodiments and advantages ofthe present invention will be apparent to those skilled in the art andare contemplated herein.

1. A method of providing collection data to a portable device,comprising: accessing a mobile collection application with afield-portable computing device associated with a field agent, where thefield-portable computing device comprises a wireless interface and adisplay configured to interact with a stylus; retrieving a list ofcollection cases from a collection data center server with the mobilecollection application; displaying the list of collection cases on thedisplay of the field-portable computing device; receiving with thefield-portable computing device a selected collection case entry from acollection case entry in the list of collection cases; generating adetailed collection case report based on the selected collection caseentry; and displaying the detailed collection case report on the displayof the field-portable computing device.
 2. The method of claim 1,further comprising: receiving a user input to the field-portablecomputing device as a function of at least one of an actuation of a key,an interaction of the stylus with the display or a combination thereof.3. The method of claim 1, further comprising: encrypting a messagepassed between the field-portable computing device and the collectiondata center server.
 4. The method of claim 1, further comprising:tailoring the list of collection cases for the field agent based on atleast one of a personal task list associated with the field agent, apersonal calendar associated with the field agent, or a combinationthereof.
 5. The method of claim 1, further comprising: receiving aselection of a link to a payment plan component included in the detailedcollection case report based on at least one of the stylus interactingwith the display, actuation of a key entry, or a combination thereof. 6.The method of claim 1, wherein the detailed collection case reportincludes a collection case balance and a link to a payment plancomponent, the method further comprising: the field-portable computingdevice receiving a user selection of the link to the payment plancomponent included in the detailed collection case report; creating withthe field-portable computing device a payment plan for the collectioncase balance with the payment plan component; and the field-portablecomputing device transmitting the payment plan to the collection datacenter server for approval.
 7. The method of claim 6, furthercomprising: the collection data center server accepting the payment planin response to receipt of the payment plan from the field-portablecomputing device; and the collection data center server updating acollection database located on the collection data center server inresponse to acceptance of the payment plan.
 8. The method of claim 6,further comprising: printing a receipt that includes a summary of thepayment plan with a printer connected with the wireless field-portablecomputing device.
 9. The method of claim 1, wherein the field-portablecomputing device is configured to permit the field agent to retainphysical possession of the field-portable computing device while thefield agent interacts with a debtor associated with the selectedcollection case entry.
 10. A mobile collection system, comprising: acollection data center server comprising a collection database incommunication with a wireless access network; a portable computingdevice comprising a wireless interface configured to communicate withthe wireless access network, and a user interface configured to interactwith a stylus to receive a user input to the user interface, wherein thecollection data center server is configured to communicate through thewireless access network to the portable computing device; anauthentication module stored on a computer readable memory accessible.by the collection data center server and executable on the collectiondata center server to log a field agent into a mobile collectionapplication executable on the portable computing device; a collectioncase inventory module stored on a computer readable memory of theportable computing device and executable on the portable computingdevice to retrieve a list of collection cases from the collection datacenter server over the wireless access network; and a collection casedetail component stored on the computer readable memory of the portablecomputing device and executable on the portable computing device togenerate a detailed collection case report in response to a userselection of a collection case entry included in the list of collectioncases.
 11. The mobile collection system of claim 10, further comprising:a payment plan component stored on the computer readable memory of theportable computing device, and executable on the portable computingdevice to automatically set up a payment plan for a collection casebalance associated with the selected collection case entry, wherein thepayment plan component is further configured to transmit the paymentplan to the collection data center server to obtain a payment planapproval.
 12. The mobile collection system of claim 10, furthercomprising: a collection case search component stored on the computerreadable memory of the portable computing device, and executable on theportable computing device to send a search request to the collectiondata center server, wherein response, the collection data centersearches a collection database located on the collection data centerserver for at least one collection case and to display on a display ofthe portable computing device a search result generated by thecollection data center server that is responsive to the search request.13. The mobile collection system of claim 12, further comprising:program code stored on the computer readable memory accessible by thecollection data center server, and executable on the collection datacenter server to generate the search result in response to the searchrequest sent by the portable computing device.
 14. The mobile collectionsystem of claim 10, where the collection case detail component isfurther exactable to modify a data field contained in the detailedcollection case report in response to detection of an interactionbetween the stylus and a display of the portable computing device. 15.The mobile collection system of claim 14, further comprising asynchronization component stored on the computer readable memory of theportable computing device and executable to synchronize a collectioncase file associated with the selected collection case entry based onthe modification made to the data field.